User-configurable activation of card applets

ABSTRACT

Card applets associated with an electronic wallet are activated and deactivated based on user-defined rules. Based on the rules and a device state, a card emulation state and card applet states are modified to enable or disable completion of transactions. The transactions are between a computing device and a reader such as a point-of-sale terminal. In some embodiments, a user designates a plurality of the card applets as fast cards capable of completing a transaction via near-field communication (NFC) interaction without user input at a time of the transaction.

BACKGROUND

Short-range wireless communication protocols enable a computing deviceto communicate with readers proximate to the computing device. Forexample, radio frequency identification (RFID), BLUETOOTH brandcommunications, Wi-Fi, and near-field communication (NFC) technologyenable a user to perform actions with the computing device such ascompleting a financial transaction, gaining access to a building, andgaining entry to a transit system. Existing systems have an electronicwallet that stores a plurality of cards. In some of the existingsystems, however, the user is limited to manually selecting andactivating one of the cards to complete a transaction. In some of theexisting systems where each of the cards remains activated at all times,the reader, rather than the user, chooses among the activated cards tocomplete a transaction.

SUMMARY

Embodiments of the disclosure selectively activate card applets on acomputing device for completing point-of-sale transactions. A devicestate for a computing device is determined. The computing device has anelectronic wallet having a plurality of card applets stored therein.Each of the card applets has a card applet state. A card emulation stateis adjusted based on the determined device state. A plurality ofuser-defined rules for each of the plurality of card applets isaccessed. The card applet states are adjusted based on the adjusted cardemulation state and the accessed plurality of user-defined rules toenable or disable point-of-sale transactions via the plurality of cardapplets.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an exemplary block diagram illustrating an architecture forinstalling card applets on a secure element in a computing device.

FIG. 2 is an exemplary block diagram illustrating a computing devicestoring a plurality of card applets.

FIG. 3 is an exemplary flow chart illustrating operation of thecomputing device to enable or disable card applets based on card appletstates and a card emulation state.

FIG. 4 is an exemplary diagram illustrating a user interface element forconfiguring settings associated with an electronic wallet.

FIG. 5 is an exemplary diagram illustrating a user interface elementdisplaying a set of fast cards selected and configured by a user.

FIG. 6A is an exemplary diagram illustrating a user interface elementfor selecting a manually-activated card for a transaction.

FIG. 6B is an exemplary diagram illustrating a user interface elementfor completing a transaction using a selected manually-activated card.

Corresponding reference characters indicate corresponding partsthroughout the drawings.

DETAILED DESCRIPTION

Referring to the figures, embodiments of the disclosure selectivelyenable or disable card applets 208 based at least on user-defined rules214 that operate, in some embodiments, responsive to user actions. Acard emulation state 212 and card applet states 210 associated with thecard applets 208 are adjusted or modified based on device state and theuser-defined rules 214. In some embodiments, a user 202 chooses whichcard applets 208 in an electronic wallet 207 are to be activatedmanually to complete a transaction (e.g., manually-activated cards), andwhich card applets 208 remain active to complete a transaction withoutuser 202 input at a time of the transaction (e.g., fast cards). For eachof the fast cards, the user 202 may further configure the availability,conditions, or criteria for activating the fast card, as well asenabling card emulation. The manually-activated cards may also bereferred to as “slow cards” or “one-time-use cards.” In someembodiments, the manually-activated cards are used to complete only onetransaction after being activated. To use one of the manually-activatedcards again, the user 202 re-activates the manually-activated card.

While some embodiments are described herein with reference tointeractions via near-field communication (NFC), aspects of thedisclosure are operable with any wireless communication protocolincluding, for example, the BLUETOOTH brand wireless communicationsprotocol. Further, while some embodiments are described herein withreference to interactions between a computing device 102 and apoint-of-sale terminal, aspects of the disclosure are operable withinteractions between the computing device 102 and any reader 224, orother computing device. Still further, while some embodiments aredescribed herein with reference to point-of-sale transactions betweenthe computing device 102 and the reader 224, such as those relating tothe acquisition of goods and/or services, aspects of the disclosure areoperable with any transactions. For example, the transactions mayinclude transactions not associated with goods and/or services, such asproviding user 202 identification, location information, contactinformation, and the like.

Referring next to FIG. 1, an exemplary block diagram illustrates anarchitecture for installing card applets 208 on a secure element 114 inthe computing device 102. The computing device 102 illustrated in FIG. 1includes one or more applications 104, a wallet core 106 (e.g., logicfor implementing the electronic wallet 207), an NFC platform 108 forimplementing NFC interactions, and an underlying operating system (OS)platform 112. The computing device 102 also includes the secure element114, chip, or other hardware component on the computing device 102 forstoring, among other items, one or more card applets 208. The secureelement 114 is accessible to the OS platform 112 and to one or more ofthe readers 224 that are in proximity of the computing device 102. Thesecure element 114 may be stored in various places on the computingdevice 102, such as on a motherboard or a universal integrated circuitcard (UICC) (e.g., or other removable storage card). The secure element114 cryptographically protects the information stored thereon (e.g., thecard applets 208).

The applications 104 on the computing device 102 communicate withapplication services 116. Communication between the computing device 102and the application services 116 (or other services or devices) mayoccur via one or more networks using any protocol or mechanism over anywired or wireless connection. Each of the application services 116communicates with a service provider trusted service manager (TSM) 118.The service provider TSM 118 communicates with a primary device TSM 120.The primary device TSM 120 communicates state and/or status with amobile network operator (MNO) plug-in 110 or other component that isassociated with the NFC platform 108 on the computing device 102. TheMNO plug-in 110 communicates with the secure element 114 to install cardapplets 208 received from the primary device TSM 120. For example, thecard applets 208 are installed via over-the-air (OTA) installation.

Referring next to FIG. 2, an exemplary block diagram illustrates thecomputing device 102 storing a plurality of the card applets 208. In theexample of FIG. 2, the computing device 102 represents a system forselectively activating one or more card applets 208 on the computingdevice 102 for completing any quantity of point-of-sale transactionswith one or more of the readers 224 (e.g., point-of-sale terminals). Thecomputing device 102 represents any device executing instructions (e.g.,as application programs, operating system functionality, or both) toimplement the operations and functionality associated with the computingdevice 102. The computing device 102 may include a mobile computingdevice or any other portable device. In some embodiments, the mobilecomputing device includes a mobile telephone, laptop, tablet, computingpad, netbook, gaming device, and/or portable media player. The computingdevice 102 may also include less portable devices such as desktoppersonal computers, kiosks, and tabletop devices. Additionally, thecomputing device 102 may represent a group of processing units or othercomputing devices.

In some embodiments, the computing device 102 has at least one processor204, at least one memory area 206, and at least one user interface (notshown). The processor 204 includes any quantity of processing units, andis programmed to execute computer-executable instructions forimplementing aspects of the disclosure. The instructions may beperformed by the processor 204 or by multiple processors executingwithin the computing device 102, or performed by a processor external tothe computing device 102. In some embodiments, the processor 204 isprogrammed to execute instructions such as those illustrated in thefigures (e.g., FIG. 3).

In some embodiments, the processor 204 represents an implementation ofanalog techniques to perform the operations described herein. Forexample, the operations may be performed by an analog computing deviceand/or a digital computing device.

The computing device 102 further has one or more computer readable mediasuch as the memory area 206. The memory area 206 includes any quantityof media associated with or accessible by the computing device 102. Thememory area 206 may be internal to the computing device 102 (as shown inFIG. 2), external to the computing device 102 (not shown), or both (notshown). In some embodiments, the memory area 206 includes read-onlymemory and/or memory wired into an analog computing device.

The memory area 206 stores, among other data, one or more applications104. The applications 104, when executed by the processor 204, operateto perform functionality on the computing device 102. Exemplaryapplications 104 include mail application programs, web browsers,calendar application programs, address book application programs,messaging programs, media applications, location-based services, searchprograms, and the like. The applications 104 may communicate withcounterpart applications or services (e.g., application services 116)such as web services accessible via a network. For example, theapplications 104 may represent downloaded client-side applications thatcorrespond to server-side services (e.g., application services 116)executing in a cloud.

The memory area 206 further stores the electronic wallet 207 having aplurality of card applets 208 stored therein, such as card applet #1through card applet #N. Each of the card applets 208 is associated withan electronic wallet item or card. For example, the card applets 208 maycorrespond to payment applets (e.g., credit or debit), access applets(e.g., for gaining access to a building or other area), loyalty applets,transit applets, coupon applets, and gift card applets.

Each of the plurality of card applets 208 has one of the card appletstates 210 associated therewith, such as card applet state #1 throughcard applet state #N. In some embodiments, each card applet 208maintains its corresponding card applet state 210. The card appletstates 210 may be read into the OS via an application programminginterface (API) or may be published to the OS by the card applets 208.For example, another applet in the secure element 114 may centralize thecard applet states 210 and respond to queries via the API or publish thecard applet states 210. In some embodiments, each card applet state 210stores data indicating whether the corresponding card applet 208 isactive or inactive (e.g., available or unavailable to the reader 224,respectively) and installed or uninstalled.

The memory area 206 also stores the card emulation state 212. The cardemulation state 212 affects the availability of the electronic wallet207 for completing transactions. For example, the card emulation state212 may enable or disable NFC interactions between the computing device102 and the reader 224, thus acting as a global setting that can enableor disable point of sale transactions without changing any of the cardapplet states 210.

While the electronic wallet 207, card applets 208, card applet states210, and card emulation state 212 are shown as being logically stored inmemory area 206, some of this data may be physically stored elsewhere onthe computing device 102 in some embodiments. For example, the secureelement 114 (e.g., a module that is outside the memory area 206) maystore the card applets 208 while the memory area 206 stores the cardapplet states 210 in the electronic wallet 207. In such embodiments, theelectronic wallet 207 may store metadata describing the card applets208, such as a representation of the card applets 208 as well as a linkfrom each of the card applet states 210 in the electronic wallet 207 tothe corresponding card applets 208 physically stored in the secureelement 114.

Further, in some embodiments, the card emulation state 212 may bephysically stored in an NFC driver and/or hardware outside, or separatefrom, the memory area 206.

The user 202 interacts with the computing device 102, as describedbelow, to define, provide, or make accessible one or more of the rules214. For example, the user 202 may draft the rules 214 or may select orchoose among pre-defined, suggested, or recommended rules. Theuser-defined rules 214 are stored in the memory area 206, and affect theavailability of the electronic wallet 207 and the card applets 208therein. For example, the user-defined rules 214 may separate the cardapplets 208 into categories, such as fast cards and slow cards (e.g.,manually-activated cards). Card applets 208 designated as fast cards arecapable of completing transactions without explicit or manual selection,use, authorization, and/or confirmation input by the user 202. In someembodiments, card applets 208 designated as fast cards are available tothe readers 224 without explicit or manual selection by the user 202,but the readers 224 may still attempt to challenge (e.g., authenticate)the user 202 by, for example, asking for a personal identificationnumber (PIN). Further, fast cards may remain active after completing atransaction, or may be deactivated after completing the transaction(e.g., depending on the user-defined rules 214).

In contrast, card applets 208 designated as manually-activated cards arecapable of completing transactions only with explicit or manualselection, use, authorization, and/or confirmation input by the user202.

The rules 214 may also identify other criteria for enabling or disablingthe card applets 208. For example, the rules 214 may identify a locationfor the computing device 102 at which the card applet 208 is enabled.The rules 214 may also identify a time of day or durations during whichthe card applet 208 is enabled. For example, the user 202 may associatea duration with one of the card applets 208 designated as a fast cardsuch that the fast card deactivates after expiration of the duration.

The memory area 206 further stores one or more computer-executablecomponents. Exemplary components include an interface component 216, acontext component 218, a driver component 220, and a transactionpreparation component 222. Operation of these components, when executed,is described below with reference to FIG. 3.

In some embodiments, the user interface includes a display (e.g., atouch screen display) and/or computer-executable instructions (e.g., adriver) for operating the display. The user interface may also includeone or more of the following to provide data to the user 202 or receivedata from the user 202: speakers, a sound card, a camera, a microphone,a vibration motor, one or more accelerometers, a BLUETOOTH brandcommunication module, global positioning system (GPS) hardware, and aphotoreceptive light sensor. For example, the user 202 may inputcommands or manipulate data by moving the computing device 102 in aparticular way.

Referring next to FIG. 3, an exemplary flow chart illustrates operationof the computing device 102 to enable or disable one or more of the cardapplets 208 based on the card applet states 210 and the card emulationstate 212. While the operations illustrated in FIG. 3 are described asbeing executed by the computing device 102, aspects of the disclosureare operable with other entities executing one or more of theoperations. For example, one or more of the operations may be executedby a server remote from the computing device 102 yet in communicationwith the computing device 102.

At 302, the computing device 102 determines a device state. Determiningthe device state includes, but is not limited to, determining a hardwarestate and/or a software state. Determining the hardware state includesdetermining, for example, whether a display of the computing device 102is on or off, and whether the computing device 102 is powered on or off.Determining the software state includes determining a current executioncontext. The execution context, for example, describes one or more ofthe applications 104 currently being executed by the computing device102. As another example, the execution context also identifies one ormore of the following: whether the electronic wallet 207 is open orclosed, whether the electronic wallet 207 is in a foreground of the userinterface in the computing device 102 or in the background, and whetherthe computing device 102 is locked or unlocked. In some embodiments, theelectronic wallet 207 and/or the card applets 208 may be locked and/orunlocked with a PIN or other security measure.

At 304, the computing device 102 adjusts or modifies the card emulationstate 212 based on the determined device state. For example, thecomputing device 102 may adjust the card emulation state 212 to beactive or inactive. If the card emulation state 212 is set to active,then one or more of the card applets 208 may be available fortransactions, depending on the corresponding card applet states 210. Ifthe card emulation state 212 is set to inactive, then none of the cardapplets 208 is available for transactions, regardless of thecorresponding card applet states 210. For example, modifying the cardemulation state 212 includes enabling or disabling NFC interactionbetween the computing device 102 and the reader 224.

In some embodiments, the computing device 102 accesses a plurality ofthe user-defined rules 214. For each of the plurality of card applets208, the user-defined rules 214 represent settings or configurationsdefining the conditions under which the card applets 208 are availableor unavailable for transactions. For example, the user-defined rules 214may designate one or more of the card applets 208 as fast cards, asdescribed above, that are capable of completing point-of-saletransactions without explicit user 202 input.

The card emulation state 212 may also be adjusted based on theuser-defined rules 214. For example, if the user-defined rules 214specify that none of the card applets 208 should be available when thecomputing device 102 is powered off, the computing device 102 adjuststhe card emulation state 212 to “inactive” when the computing device 102powers off, thus disabling each of the card applets 208 (e.g.,preventing the card applets 208 from completing transactions while thecomputing device 102 is powered off).

At 306, the computing device 102 adjusts or modifies the card appletstates 210 based on the adjusted card emulation state 212 and theuser-defined rules 214 to enable or disable point-of-sale transactionsvia the plurality of card applets 208. For example, one of the cardapplet states 210 may be set to inactive or otherwise disabled, thusmaking the corresponding card applet 208 unavailable for transactions.In another example, one of the card applet states 210 may be set toactive or otherwise enabled, thus making the corresponding card applet208 available for transactions.

In general, the card emulation state 212 and/or the card applet states210 are used to control the availability of the card applets 208. Insome embodiments, the card emulation state 212 is adjusted to controlwhen card applets 208 designated as fast cards are available, while thecard applet states 210 are used to designate which of the card applets208 are fast cards. Other embodiments, however, lack the card emulationstate 212. In such embodiments, the card applet states 210 are used bothto control when the card applets 208 are available and to designatewhich of the card applets 208 are fast cards.

In embodiments in which the user-defined rules 214 identify some cardapplets 208 as fast cards and other card applets 208 asmanually-activated cards, the computing device 102 may adjust the cardapplet states 210 to enable the fast cards when the electronic wallet207 is open. Alternatively or in addition, the computing device 102 mayadjust the card applet states 210 to enable the fast cards when adisplay of the computing device 102 is on. As another example, thecomputing device 102 may adjust the card applet states 210 to disablethe fast cards when the computing device 102 is locked. In still anotherexample, the computing device 102 may adjust the card applet states 210to keep the fast cards enabled even when the computing device 102 ispowered off In such an example, the fast cards obtain power to completetransactions via the mechanism involved in the communication between thesecure element 114 and the reader 224. For example, during an NFCinteraction, power is derived from an electromagnetic field provided bythe reader 224.

Adjusting the card applet states 210 produces a set of one or more ofthe card applets 208 that are available for transactions. If apoint-of-sale terminal or other reader 224 is detected at 308, thecomputing device 102 presents, or otherwise makes available, theavailable set of card applets 208 (e.g., enabled) at 310 for completingthe transaction. Selection of one of the available card applets 208 mayoccur according to any selection process, as known in the art.

While examples of the user-defined rules 214 have been described herein,aspects of the disclosure are operable with any rules that affect theavailability of the card applets 208 for completing transactions.

In some embodiments, the computer-executable components illustrated inFIG. 2 execute to perform one or more of the operations illustrated inFIG. 3. For example, the interface component 216, when executed by atleast one processor 204 of the computing device 102, causes theprocessor 204 to present to the user 202 the electronic wallet 207 in auser interface element and to receive, from the user 202 via the userinterface element, one or more of the user-defined rules 214. Theuser-defined rules 214 correspond to the electronic wallet 207 and/orthe plurality of card applets 208 displayed in the electronic wallet207.

The context component 218, when executed by at least one processor 204of the computing device 102, causes the processor 204 to determine adevice state for the computing device 102. The driver component 220,when executed by at least one processor 204 of the computing device 102,causes the processor 204 to adjust the card emulation state 212 based onthe device state determined by the context component 218. Thetransaction preparation component 222, when executed by at least oneprocessor 204 of the computing device 102, causes the processor 204 toadjust the card applet states 210 based on the card emulation state 212adjusted by the driver component 220 and the one or more user-definedrules 214 received by the interface component 216 to enable or disablepoint-of-sale transactions via the plurality of card applets 208.

Referring next to FIG. 4, an exemplary diagram illustrates a userinterface element 402 for configuring settings associated with theelectronic wallet 207. While the user interface element 402 illustratedin FIG. 4 shows a set of exemplary configurations on a mobile telephone,aspects of the disclosure are operable with any quantity or type ofsettings or configurations on any mobile device. In the example of FIG.4, the user 202 has provided a password for entry to make purchases viaan online marketplace. The user 202 has also enabled NFC transactions.

The user interface element 402 further illustrates a set ofconfiguration options for selection by the user 202. In this example,the configuration options relate to enabling the user-selected set offast cards (1) only when the electronic wallet 207 is open, (2) when themobile telephone is unlocked, (3) anytime the screen or display of themobile telephone is on, or (4) even when the mobile telephone is powereddown or off If the user 202 selects option (1), the mobile telephoneturns on card emulation (e.g., adjust the card emulation state 212 toallow any card applet 208 with a corresponding card applet state 210 of“active” to complete a transaction) when the user 202 opens theelectronic wallet 207. The mobile telephone turns off card emulation(e.g., adjusts the card emulation state 212 to disable each of the cardapplets 208, regardless of the corresponding card applet states 210) assoon as the user 202 closes the electronic wallet 207 or switches toanother user interface element.

If the user 202 selects option (2), the mobile telephone turns on cardemulation when the user 202 unlocks the mobile telephone and turns offcard emulation when the user 202 locks the mobile telephone. If the user202 selects option (3), the mobile telephone turns on card emulationwhen the user 202 turns on the display, even if the mobile telephone islocked. The mobile telephone turns off card emulation when the user 202turns off the display. If the user 202 selects option (4), the mobiletelephone keeps card emulation on even when the mobile telephone isturned off. In this option, card emulation may remain on even if abattery is removed from the mobile telephone (e.g., depending on whetherhardware associated with the mobile telephone uses any power from thebattery).

In the example of FIG. 4, the user 202 has selected option (1), thusenabling the selected set of fast cards only when the electronic wallet207 is open (e.g., the electronic wallet 207 is in the foreground of thedisplay of the mobile telephone).

Additional user-defined rules 214 (not shown) may indicate whether themobile telephone prompts for a password to open the electronic wallet207 or unlock the mobile telephone.

Referring next to FIG. 5, an exemplary diagram illustrates a userinterface element 502 displaying a set of fast cards selected andconfigured by the user 202. In some embodiments, the user interfaceelement 502 represents the electronic wallet 207. In this example, theuser 202 has selected four card applets to be “fast cards,” or otherwiseactivated the four card applets as described above. The fast cards areshown on the left side of the user interface element 502, while a listof the available cards is shown on the right side of the user interfaceelement 502. The available cards include both fast cards (e.g., active)and manually-activated cards (e.g., inactive). The user 202 maydesignate one or more of the available cards as fast cards by, forexample, selecting a menu item or dragging the card to the set of fastcards.

Referring next to FIG. 6A, an exemplary diagram illustrates a userinterface element 602 for selecting a manually-activated card for atransaction. In the example of FIG. 6A, the user 202 opens theelectronic wallet 207 and reviews the set of card applets (e.g., bysliding through each of the card applets). The mobile telephone promptsthe user 202 to select the currently presented card applet to complete atransaction. The user interface element 602 provides informationrelating to the presented card applet, such as a company name, availablecredit, and a link or other reference to execute an application (e.g.,one of the applications 104) associated with the card applet.

Referring next to FIG. 6B, an exemplary diagram illustrates a userinterface element 604 for completing a transaction using a selectedmanually-activated card. Continuing the example from FIG. 6A, the user202 has selected or tapped on the presented card applet. The mobiletelephone adjusts the card applet state 210 for the selected card appletto “active.” The user interface element 604 in FIG. 6B then prompts theuser 202 to complete the transaction. The user 202 taps on the displayto complete the transaction using the selected, activated card applet.Because the card applet is a manually-activated card, the mobiletelephone adjusts the card applet state 210 of the selected card appletto disable or deactivate the card applet after the transactioncompletes.

Further, after the transaction completes, the mobile telephone mayoperate to reactivate one or more of the fast cards that weredeactivated to enable use of the manually-activated card. For example,in environments where only one payment card may be active at any giventime, in response to the user 202 activating one of themanually-activated cards, the mobile telephone deactivates any otheractive payment cards that have been designated as fast cards. After thetransaction with the manually-activated card completes, the mobiletelephone re-activates the fast card(s) that were de-activated.

Additional Examples

In some embodiments, the user-defined rules 214 specify locations forenabling one or more of the card applets 208 designated as fast cards.Such embodiments provide the user 202 with the capability to specify onecard applet 208 (e.g., corresponding to a business credit card) as oneof the fast cards available only while the user 202 is near a locationdesignated as a workplace. Similarly, the user 202 may specific adifferent card applet 208 (e.g., corresponding to a personal creditcard) as one of the fast cards available in locations other than thedesignated workplace location.

The user-defined rules 214 may also specify times during which one ormore of the card applets 208 designated as fast cards are available. Forexample, the user 202 may specify that one card applet 208 (e.g.,corresponding to a business credit card) as one of the fast cardsavailable only during business hours. The user 202 may specify adifferent card applet 208 (e.g., corresponding to a personal creditcard) as one of the fast cards available during times other thanbusiness hours.

In some embodiments, the card emulation state 212 and/or one or more ofthe card applet states 210 may be adjusted by the user 202 pressing oneor more physical elements of the computing device 102. For example, thecomputing device 102 may include one or more buttons (e.g., virtual orphysical) that the user 202 pushes to activate or deactivate one or moreof the card applets 208. The user 202 may toggle the card emulationstate 212 and/or one or more of the card applet states 210 in thismanner, or the user 202 may push and hold the buttons to adjust thestates. Further, some embodiments contemplate the computing device 102including security elements such as a fingerprint reader to authenticatethe user 202 before adjusting the card emulation state 212 and/or thecard applet states 210.

At least a portion of the functionality of the various elements in FIG.1 and FIG. 2 may be performed by other elements in FIG. 1 or FIG. 2, oran entity (e.g., processor, web service, server, application program,computing device, etc.) not shown in FIG. 1 or FIG. 2.

In some embodiments, the operations illustrated in FIG. 3 may beimplemented as software instructions encoded on a computer readablemedium, in hardware programmed or designed to perform the operations, orboth. For example, aspects of the disclosure may be implemented as asystem on a chip or other circuitry including a plurality ofinterconnected, electrically conductive elements.

While no personally identifiable information is tracked by aspects ofthe disclosure, embodiments have been described with reference to datamonitored and/or collected from users 202. In such embodiments, noticeis provided to the users 202 of the collection of the data (e.g., via adialog box or preference setting) and users 202 are given theopportunity to give or deny consent for the monitoring and/orcollection. The consent may take the form of opt-in consent or opt-outconsent.

Exemplary Operating Environment

Exemplary computer readable media include flash memory drives, digitalversatile discs (DVDs), compact discs (CDs), floppy disks, and tapecassettes. By way of example and not limitation, computer readable mediacomprise computer storage media and communication media. Computerstorage media include volatile and nonvolatile, removable andnon-removable media implemented in any method or technology for storageof information such as computer readable instructions, data structures,program modules or other data. Computer storage media are tangible,exclude propagated data signals, and are mutually exclusive tocommunication media. In some embodiments, computer storage media areimplemented in hardware. Exemplary computer storage media include harddisks, flash drives, and other solid-state memory. In contrast,communication media typically embody computer readable instructions,data structures, program modules, or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includeany information delivery media.

Although described in connection with an exemplary computing systemenvironment, embodiments of the disclosure are capable of implementationwith numerous other general purpose or special purpose computing systemenvironments, configurations, or devices.

Examples of well-known computing systems, environments, and/orconfigurations that may be suitable for use with aspects of theinvention include, but are not limited to, mobile computing devices,personal computers, server computers, hand-held or laptop devices,multiprocessor systems, gaming consoles, microprocessor-based systems,set top boxes, programmable consumer electronics, mobile telephones,network PCs, minicomputers, mainframe computers, distributed computingenvironments that include any of the above systems or devices, and thelike. Such systems or devices may accept input from the user 202 in anyway, including from input devices such as a keyboard or pointing device,via gesture input, and/or via voice input.

Embodiments of the invention may be described in the general context ofcomputer-executable instructions, such as program modules, executed byone or more computers or other devices. The computer-executableinstructions may be organized into one or more computer-executablecomponents or modules. Generally, program modules include, but are notlimited to, routines, programs, objects, components, and data structuresthat perform particular tasks or implement particular abstract datatypes. Aspects of the invention may be implemented with any number andorganization of such components or modules. For example, aspects of theinvention are not limited to the specific computer-executableinstructions or the specific components or modules illustrated in thefigures and described herein. Other embodiments of the invention mayinclude different computer-executable instructions or components havingmore or less functionality than illustrated and described herein.

Aspects of the invention transform a general-purpose computer into aspecial-purpose computing device when configured to execute theinstructions described herein.

The embodiments illustrated and described herein as well as embodimentsnot specifically described herein but within the scope of aspects of theinvention constitute exemplary means for selectively activating one ormore of the plurality of card applets 208 on the mobile computing devicefor completing point-of-sale transactions.

The order of execution or performance of the operations in embodimentsof the invention illustrated and described herein is not essential,unless otherwise specified. That is, the operations may be performed inany order, unless otherwise specified, and embodiments of the inventionmay include additional or fewer operations than those disclosed herein.For example, it is contemplated that executing or performing aparticular operation before, contemporaneously with, or after anotheroperation is within the scope of aspects of the invention.

When introducing elements of aspects of the invention or the embodimentsthereof, the articles “a,” “an,” “the,” and “said” are intended to meanthat there are one or more of the elements. The terms “comprising,”“including,” and “having” are intended to be inclusive and mean thatthere may be additional elements other than the listed elements.

Having described aspects of the invention in detail, it will be apparentthat modifications and variations are possible without departing fromthe scope of aspects of the invention as defined in the appended claims.As various changes could be made in the above constructions, products,and methods without departing from the scope of aspects of theinvention, it is intended that all matter contained in the abovedescription and shown in the accompanying drawings shall be interpretedas illustrative and not in a limiting sense.

What is claimed is:
 1. A system for selectively activating card appletson a mobile computing device for completing point-of-sale transactions,said system comprising: a memory area associated with the mobilecomputing device, said memory area storing an electronic wallet having aplurality of card applets stored therein, each of the plurality of cardapplets having a card applet state; and a processor programmed to:receive, from a user of the mobile computing device, a plurality ofuser-defined rules corresponding to the plurality of card applets;determine a device state for the mobile computing device; modify a cardemulation state based on the determined device state to enable ordisable near-field communications between the mobile computing deviceand a point-of-sale terminal; and modify one or more of the card appletstates based on the modified card emulation state and the receivedplurality of user-defined rules to enable or disable point-of-saletransactions via the plurality of card applets.
 2. The system of claim1, wherein the processor is programmed to modify the one or more of thecard applet states by designating one or more of the plurality of cardapplets as fast cards that complete point-of-sale transactions withoutexplicit user input.
 3. The system of claim 1, wherein the processor isprogrammed to modify the one or more of the card applet states bydesignating one or more of the plurality of card applets asmanually-activated cards that complete point-of-sale transactions onlywith explicit user input.
 4. The system of claim 1, wherein thepoint-of-sale transactions relate to acquiring goods and/or services. 5.The system of claim 1, further comprising means for selectivelyactivating one or more of the plurality of card applets on the mobilecomputing device for completing point-of-sale transactions.
 6. A methodcomprising: determining a device state for a computing device, saidcomputing device having an electronic wallet associated therewith, saidelectronic wallet having a plurality of card applets stored therein eachhaving a card applet state; accessing a plurality of user-defined rulesfor each of the plurality of card applets; and adjusting the card appletstates based on the determined device state and the accessed pluralityof user-defined rules to enable or disable transactions via theplurality of card applets.
 7. The method of claim 6, wherein adjustingthe card applet states comprises enabling one or more of the pluralityof card applets.
 8. The method of claim 7, further comprising presentingthe enabled one or more of the plurality of card applets to apoint-of-sale terminal.
 9. The method of claim 6, wherein determiningthe device state comprises determining a hardware state and/or asoftware state.
 10. The method of claim 6, wherein determining thedevice state comprises determining a software state describing one ormore application programs executing on the computing device.
 11. Themethod of claim 6, wherein determining the device state comprisesdetermining one or more of the following: whether the electronic walletis open, whether the electronic wallet is in a foreground of a userinterface in the computing device, whether the computing device islocked, whether the computing device is unlocked, whether a display ofthe computing device is on, whether a display of the computing device isoff, whether the computing device is powered on, and whether thecomputing device is powered off
 12. The method of claim 6, furthercomprising adjusting a card emulation state based at least on thedetermined device state, and wherein adjusting the card applet statescomprises adjusting the card applet states based on the adjusted cardemulation state and the accessed plurality of user-defined rules. 13.The method of claim 6, wherein adjusting the card applet statescomprises, for each of the card applet states, setting the card appletstate to active or inactive.
 14. The method of claim 6, wherein theaccessed plurality of user-defined rules designate one or more of theplurality of card applets as fast cards that complete the transactionswithout explicit user input.
 15. The method of claim 14, whereinadjusting the card applet states comprises enabling the fast cards whenthe electronic wallet is open and/or when a display of the computingdevice is on.
 16. The method of claim 14, wherein adjusting the cardapplet states comprises disabling the fast cards when the computingdevice is locked.
 17. The method of claim 14, wherein adjusting the cardapplet states comprises keeping the fast cards enabled when thecomputing device is powered off
 18. One or more computer storage mediaembodying computer-executable components, said components comprising: aninterface component that when executed causes at least one processor to:present, to a user of a computing device, an electronic wallet in a userinterface element, the electronic wallet having a plurality of cardapplets therein, each of the plurality of card applets having a cardapplet state associated therewith, and receive, from the user via theuser interface element, one or more user-defined rules corresponding tothe electronic wallet and/or the plurality of card applets displayed inthe electronic wallet; a context component that when executed causes atleast one processor to determine a device state for the computingdevice; a driver component that when executed causes at least oneprocessor to adjust a card emulation state based on the device statedetermined by the context component; and a transaction preparationcomponent that when executed causes at least one processor to adjust thecard applet states based on the card emulation state adjusted by thedriver component and the one or more user-defined rules received by theinterface component to enable or disable point-of-sale transactions viathe plurality of card applets.
 19. The computer storage media of claim18, wherein the user-defined rules received by the interface componentidentify, for each of the plurality of card applets, a location for thecomputing device at which the card applet is enabled.
 20. The computerstorage media of claim 18, wherein the user-defined rules received bythe interface component identify, for each of the plurality of cardapplets, a time of day during which the card applet is enabled.